Skip to content

Conversation

@Tacioandrade
Copy link

Hello! I'm sharing a feature I needed to make the work of the N2 support teams at the companies I work with easier.

I have some clients with specific source blocking policies, among other things, that the client's N2 support team always ended up getting wrong when configuring. For this reason, I developed this feature.

On the Proxy Hosts screen, in addition to Edit, Disable, and Delete, there's now a Clone button. When pressed, it opens the same Add a Proxy Host modal, but with the original Proxy Host data already filled in. You only need to change the host, IP, and port, and a new Reverse Proxy with the necessary settings is configured.

I would greatly appreciate it if you could add this feature to the official project so that you don't have to apply this patch with each new npm version.

@Tacioandrade
Copy link
Author

That's a strange error. I had managed to run it using the project's start-dev script.

However, I will fix this error and try the PR again by the end of the week. =)

@nginxproxymanagerci
Copy link

Docker Image for build 2 is available on DockerHub:

nginxproxymanager/nginx-proxy-manager-dev:pr-4975

Note

Ensure you backup your NPM instance before testing this image! Especially if there are database changes.
This is a different docker image namespace than the official image.

Warning

Changes and additions to DNS Providers require verification by at least 2 members of the community!

@Tacioandrade
Copy link
Author

I understand the problem; it was just the way I wrote a comparison that Yarn flagged as non-standard.

I adjusted it and it seems to be working. =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant